SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>NetBIOS</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">NetBIOS</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">"NetBEUI" and "NetBIOS Enhanced User Interface" redirect here. For specifically the protocol available in Microsoft Windows, see <a href="NetBIOS_Frames" title="NetBIOS Frames">NetBIOS Frames</a>. For details, see <a href="#NetBEUI">§ NetBEUI</a>.</div>

<div role="note" class="hatnote navigation-not-searchable">"Network Basic Input/Output System" redirects here. For the Network I/O System, see <a href="NIOS_(Digital_Research)" class="mw-redirect" title="NIOS (Digital Research)">NIOS (Digital Research)</a>.</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1248332772">

/* start https://en.wikipedia.org/ */

.mw-parser-output .multiple-issues-text{width:95%;margin:0.2em 0}.mw-parser-output .multiple-issues-text>.mw-collapsible-content{margin-top:0.3em}.mw-parser-output .compact-ambox .ambox{border:none;border-collapse:collapse;background-color:transparent;margin:0 0 0 1.6em!important;padding:0!important;width:auto;display:block}body.mediawiki .mw-parser-output .compact-ambox .ambox.mbox-small-left{font-size:100%;width:auto;margin:0}.mw-parser-output .compact-ambox .ambox .mbox-text{padding:0!important;margin:0!important}.mw-parser-output .compact-ambox .ambox .mbox-text-span{display:list-item;line-height:1.5em;list-style-type:disc}body.skin-minerva .mw-parser-output .multiple-issues-text>.mw-collapsible-toggle,.mw-parser-output .compact-ambox .ambox .mbox-image,.mw-parser-output .compact-ambox .ambox .mbox-imageright,.mw-parser-output .compact-ambox .ambox .mbox-empty-cell,.mw-parser-output .compact-ambox .hide-when-compact{display:none}

/* end https://en.wikipedia.org/ */

</style>

</p><p><b>NetBIOS</b> (<span class="rt-commentedText nowrap"><span class="IPA nopopups noexcerpt" lang="en-fonipa">/<span style="border-bottom:1px dotted"><span title="/ˈ/: primary stress follows">ˈ</span><span title="'n' in 'nigh'">n</span><span title="/ɛ/: 'e' in 'dress'">ɛ</span><span title="'t' in 'tie'">t</span><span title="'b' in 'buy'">b</span><span title="/aɪ/: 'i' in 'tide'">aɪ</span><span title="/ɒ/: 'o' in 'body'">ɒ</span><span title="'s' in 'sigh'">s</span></span>/</span></span>) is an acronym for <b>Network Basic Input/Output System</b>. It provides services related to the <a href="Session_layer" title="Session layer">session layer</a> of the <a href="OSI_model" title="OSI model">OSI model</a> allowing applications on separate computers to communicate over a <a href="Local_area_network" title="Local area network">local area network</a>. As strictly an <a href="API" title="API">API</a>, NetBIOS is not a <a href="Networking_protocol" class="mw-redirect" title="Networking protocol">networking protocol</a>. <a href="Operating_system" title="Operating system">Operating systems</a> of the 1980s (DOS and Novell Netware primarily) ran NetBIOS over <a href="IEEE_802.2" title="IEEE 802.2">IEEE 802.2</a> and <a href="IPX/SPX" title="IPX/SPX">IPX/SPX</a> using the <a href="NetBIOS_Frames" title="NetBIOS Frames">NetBIOS Frames</a> (NBF) and NetBIOS over IPX/SPX (NBX) protocols, respectively. In modern networks, NetBIOS normally runs over <a href="TCP/IP" class="mw-redirect" title="TCP/IP">TCP/IP</a> via the <a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NetBIOS over TCP/IP</a> (NBT) protocol. NetBIOS is also used for identifying system names in TCP/IP (Windows).

</p>

<div class="mw-heading mw-heading2"><h2 id="History_and_terminology">History and terminology</h2></div>

<p>NetBIOS is an operating system-level API that allows applications on computers to communicate with one another over a <a href="Local_area_network" title="Local area network">local area network</a> (LAN). The API was created in 1983 by <a href="Sytek_Inc" class="mw-redirect" title="Sytek Inc">Sytek Inc</a>. for software communication over <a href="IBM_PC_Network" title="IBM PC Network">IBM PC Network</a> LAN technology.<sup id="cite_ref-barrie_1-0" class="reference"><a href="#cite_note-barrie-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-inside_netbios_2-0" class="reference"><a href="#cite_note-inside_netbios-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Page: 1-1">: 1-1 </span></sup> On <a href="IBM_PC_Network" title="IBM PC Network">IBM PC Network</a>, as an API alone, NetBIOS relied on proprietary Sytek networking protocols for communication over the wire.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-inside_netbios_2-1" class="reference"><a href="#cite_note-inside_netbios-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Page: 1-1">: 1-1 </span></sup>

</p><p>In 1985, IBM went forward with the <a href="Token_Ring" title="Token Ring">Token Ring</a> network scheme and produced an <a href="Emulator" title="Emulator">emulator</a> of Sytek's NetBIOS API to allow NetBIOS-aware applications from the PC-Network era to work over IBM's new Token Ring hardware.<sup id="cite_ref-inside_netbios_2-2" class="reference"><a href="#cite_note-inside_netbios-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Page: 1-1">: 1-1 </span></sup> This IBM emulator, named NetBIOS Extended User Interface (NetBEUI),<sup id="cite_ref-inside_netbios_2-3" class="reference"><a href="#cite_note-inside_netbios-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Page: 2-2">: 2-2 </span></sup> expanded the base NetBIOS API created by Sytek with, among other things, the ability to deal with the greater node capacity of Token Ring.<sup id="cite_ref-inside_netbios_2-4" class="reference"><a href="#cite_note-inside_netbios-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Page: 2-17">: 2-17 </span></sup> A new networking protocol, <a href="NetBIOS_Frames" title="NetBIOS Frames">NBF</a>, was simultaneously produced by IBM to allow its NetBEUI API (their enhanced NetBIOS API) to provide its services over Token Ring – specifically, at the <a href="IEEE_802.2" title="IEEE 802.2">IEEE 802.2</a> <a href="Logical_Link_Control" class="mw-redirect" title="Logical Link Control">Logical Link Control</a> layer.<sup id="cite_ref-inside_netbios_2-5" class="reference"><a href="#cite_note-inside_netbios-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Pages: 3-8–3-10">: 3-8–3-10 </span></sup>

</p><p>In 1985, <a href="Microsoft" title="Microsoft">Microsoft</a> created its own implementation of the NetBIOS API for its <a href="MS-Net" title="MS-Net">MS-Net</a> networking technology. As in the case of IBM's Token Ring, the services of Microsoft's NetBIOS implementation were provided over the IEEE 802.2 Logical Link Control layer by the NBF protocol.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> However, the MS-Net was only delivered to <a href="Original_equipment_manufacturer" title="Original equipment manufacturer">OEMs</a>, and it was actually not a complete product, nor was it ready to communicate on the network in the form it was distributed. It lacked any implementation of <a href="OSI_model" title="OSI model">OSI</a> Layers 1 to 4 (<a href="Physical_layer" title="Physical layer">Physical</a>, <a href="Data_link_layer" title="Data link layer">Data link</a>, <a href="Network_layer" title="Network layer">Network</a> and <a href="Transport_layer" title="Transport layer">Transport</a> Layers) and an OEM was expected to provide these implementations (in the form of a NetBIOS part) to make its version of MS-Net a complete and ready to use product. MS-Net accessed the network through the Microsoft's own variant of NetBIOS, which was split into two parts - the lower level part that OEMs had to provide implemented the NetBIOS calls that depended on layers 1-4, while the higher level part, provided by Microsoft, was hardware- and protocol-independent. This NetBIOS implementation supported the full NetBIOS API, but was called by invoking <a href="X86" title="X86">x86</a> interrupt 0x2A, instead of IBM's standard interrupt 0x5C. The reliance on OEMs to implement parts of NetBIOS had the unfortunate side effect that different OEM versions of MS-Net and NetBIOS generally weren't able to communicate with one another. <sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p><p>In 1986, <a href="Novell" title="Novell">Novell</a> released Advanced <a href="Novell_NetWare" class="mw-redirect" title="Novell NetWare">Novell NetWare</a> 2.0 featuring the company's own emulation of the NetBIOS API. Its services were encapsulated within NetWare's <a href="IPX/SPX" title="IPX/SPX">IPX/SPX</a> protocol using the NetBIOS over IPX/SPX (NBX) protocol.

</p><p>In 1987, a method of encapsulating NetBIOS in <a href="Transmission_Control_Protocol" title="Transmission Control Protocol">TCP</a> and <a href="User_Datagram_Protocol" title="User Datagram Protocol">UDP</a> packets, <a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NetBIOS over TCP/IP</a> (NBT), was published. It was described in RFC 1001 ("Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods") and RFC 1002 ("Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications"). The NBT protocol was developed in order to "allow an implementation [of NetBIOS applications] to be built on virtually any type of system where the TCP/IP protocol suite is available," and to "allow NetBIOS interoperation in the Internet."

</p><p>After the <a href="IBM_PS/2" title="IBM PS/2">PS/2</a> computer hit the market in 1987, IBM released the PC LAN Support Program, which included a driver offering the NetBIOS API.

</p><p>There is some confusion between the names NetBIOS and NetBEUI. NetBEUI originated strictly as the <a href="Moniker" class="mw-redirect" title="Moniker">moniker</a> for IBM's enhanced 1985 NetBIOS emulator for Token Ring. The name NetBEUI should have died there, considering that at the time, the NetBIOS implementations by other companies were known simply as NetBIOS regardless of whether they incorporated the API extensions found in Token Ring's emulator. For MS-Net, however, Microsoft elected to name its implementation of the NBF protocol "NetBEUI" – naming its implementation of the transport protocol after IBM's enhanced version of the API. Consequently Microsoft file and printer sharing over <a href="Ethernet" title="Ethernet">Ethernet</a> often continues to be called NetBEUI, with the name NetBIOS commonly used only in reference to file and printer sharing over <a href="TCP/IP" class="mw-redirect" title="TCP/IP">TCP/IP</a>. More accurately, the former is <a href="NetBIOS_Frames" title="NetBIOS Frames">NetBIOS Frames</a> (NBF), and the latter is <a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NetBIOS over TCP/IP</a> (NBT).

</p><p>Since its original publication in a technical reference book from IBM, the NetBIOS API specification has become a <a href="De_facto_standard" title="De facto standard"><i>de facto</i> standard</a> in the industry despite originally supporting a maximum of only 80 PCs in a LAN. This limitation was generally overcome industry-wide through the transition from NBF to NBT, under which, for example, Microsoft was able to switch to <a href="Domain_Name_System" title="Domain Name System">Domain Name System</a> (DNS) for resolution of NetBIOS <a href="Hostname" title="Hostname">hostnames</a>, having formerly used the LAN segment-compartmentalized NBF protocol itself to resolve such names in Windows <a href="Client%E2%80%93server_model" title="Client–server model">client-server networks</a>.<sup id="cite_ref-barrie_1-1" class="reference"><a href="#cite_note-barrie-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Services">Services</h2></div>

<p>NetBIOS provides three distinct services:

</p>

<ul><li>Name service (NetBIOS-NS) for name registration and <a href="Name_resolution_(computer_systems)" title="Name resolution (computer systems)">resolution</a>.</li>

<li><a href="Datagram" title="Datagram">Datagram</a> distribution service (NetBIOS-DGM) for connectionless communication.</li>

<li><a href="Session_(computer_science)" title="Session (computer science)">Session</a> service (NetBIOS-SSN) for <a href="Connection-oriented_communication" title="Connection-oriented communication">connection-oriented communication</a>.</li></ul>

<p>(Note: <a href="Server_Message_Block" title="Server Message Block">SMB</a>, an upper layer, is a service that runs on top of the Session Service and the Datagram service, and is not to be confused as a necessary and integral part of NetBIOS itself. It can now run atop TCP with a small adaptation layer that adds a length field to each SMB message; this is necessary because TCP only provides a byte-stream service with no notion of message boundaries.)

</p>

<div class="mw-heading mw-heading3"><h3 id="Name_service">Name service</h3></div>

<p>In order to start sessions or distribute datagrams, an application must register its NetBIOS name using the name service. NetBIOS names are 16 octets in length and vary based on the particular implementation. Frequently, the 16th octet, called the NetBIOS Suffix, designates the type of resource, and can be used to tell other applications what type of services the system offers. In <a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NBT</a>, the name service operates on UDP port 137 (TCP port 137 can also be used, but rarely is).

</p><p>The name service primitives offered by NetBIOS are:

</p>

<ul><li>Add name – registers a NetBIOS name.</li>

<li>Add group name – registers a NetBIOS "group" name.</li>

<li>Delete name – un-registers a NetBIOS name or group name.</li>

<li>Find name – looks up a NetBIOS name on the network.</li></ul>

<p><a href="IPv6" title="IPv6">Internet Protocol Version 6 (IPv6)</a> are not supported by the NetBIOS name resolution protocol.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Datagram_distribution_service">Datagram distribution service</h3></div>

<p>Datagram mode is <a href="Connectionless" class="mw-redirect" title="Connectionless">connectionless</a>; the application is responsible for error detection and recovery. In <a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NBT</a>, the datagram service runs on UDP port 138.

</p><p>The datagram service primitives offered by NetBIOS are:

</p>

<ul><li>Send Datagram – send a datagram to a remote NetBIOS name.</li>

<li>Send Broadcast Datagram – send a datagram to all NetBIOS names on the network.</li>

<li>Receive Datagram – wait for a packet to arrive from a Send Datagram operation.</li>

<li>Receive Broadcast Datagram – wait for a packet to arrive from a Send Broadcast Datagram operation.</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Session_service">Session service</h3></div>

<p>Session mode lets two computers establish a connection, allows messages to span multiple packets, and provides error detection and recovery. In <a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NBT</a>, the session service runs on TCP port 139.

</p><p>The session service primitives offered by NetBIOS are:

</p>

<ul><li>Call – opens a session to a remote NetBIOS name.</li>

<li>Listen – listen for attempts to open a session to a NetBIOS name.</li>

<li>Hang Up – close a session.</li>

<li>Send – sends a packet to the computer on the other end of a session.</li>

<li>Send No Ack – like Send, but doesn't require an acknowledgment.</li>

<li>Receive – wait for a packet to arrive from a Send on the other end of a session.</li></ul>

<p>In the original protocol used to implement NetBIOS services on PC-Network, to establish a session, the initiating computer sends an Open request which is answered by an Open acknowledgment. The computer that started the session will then send a Session Request packet which will prompt either a Session Accept or Session Reject packet.

</p><p>During an established session, each transmitted packet is answered by either a positive-acknowledgment (ACK) or negative-acknowledgment (NAK) response. A NAK will prompt retransmission of the data. Sessions are closed by the non-initiating computer by sending a close request. The computer that started the session will reply with a close response which prompts the final session closed packet.

</p>

<div class="mw-heading mw-heading2"><h2 id="NetBIOS_name_vs_Internet_host_name">NetBIOS name vs Internet host name</h2></div>

<p>When NetBIOS is run in conjunction with <a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocols</a> (e.g., NBT), each computer may have multiple names: one or more NetBIOS name service names and one or more Internet host names.

</p>

<div class="mw-heading mw-heading3"><h3 id="NetBIOS_name">NetBIOS name</h3></div>

<p>The NetBIOS name is 16 ASCII characters, however Microsoft limits the host name to 15 characters and reserves the 16th character as a NetBIOS Suffix.<sup id="cite_ref-MS_7-0" class="reference"><a href="#cite_note-MS-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> This suffix describes the service or name record type such as host record, master browser record, or domain controller record or other services. The host name (or short host name) is specified when Windows networking is installed/configured, the suffixes registered are determined by the individual services supplied by the host. In order to connect to a computer running TCP/IP via its NetBIOS name, the name must be resolved to a <a href="Network_address" title="Network address">network address</a>. Today this is usually an <a href="IP_address" title="IP address">IP address</a> (the NetBIOS name to IP address resolution is often done by either broadcasts or a <a href="Windows_Internet_Name_Service" title="Windows Internet Name Service">WINS</a> Server – NetBIOS Name Server). A computer's NetBIOS name is often the same as that computer's host name (see below), although truncated to 15 characters, but it may also be completely different.

</p><p>NetBIOS names are a sequence of alphanumeric characters. The following characters are explicitly not permitted: <samp>\/:*?"<>|</samp>. Since Windows 2000, NetBIOS names also had to comply with restrictions on DNS names: they cannot consist entirely of digits, and the hyphen ("-") or full-stop (".") characters may not appear as the first or last character. Since Windows 2000, Microsoft has advised against including any full-stop (".") characters in NetBIOS names, such that applications can use the presence of a full-stop to distinguish domain names from NetBIOS names.<sup id="cite_ref-MS_7-1" class="reference"><a href="#cite_note-MS-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p><p>The Windows <a href="LMHOSTS" title="LMHOSTS">LMHOSTS</a> file provides a NetBIOS name resolution method that can be used for small networks that do not use a WINS server.

</p>

<div class="mw-heading mw-heading3"><h3 id="Internet_host_name">Internet host name</h3></div>

<p>A Windows machine's NetBIOS name is not to be confused with the computer's Internet host name (assuming that the computer is also an Internet host in addition to being a NetBIOS node, which need not necessarily be the case). Generally a computer running Internet protocols (whether it is a Windows machine or not) usually has a host name (also sometimes called a machine name). Originally these names were stored in and provided by a <a href="Hosts_(file)" title="Hosts (file)">hosts file</a> but today most such names are part of the hierarchical <a href="Domain_Name_System" title="Domain Name System">Domain Name System</a> (DNS).

</p><p>Generally the host name of a Windows computer is based on the NetBIOS name plus the Primary DNS Suffix, which are both set in the System Properties dialog box. There may also be connection-specific suffixes which can be viewed or changed on the DNS tab in Control Panel → Network → TCP/IP → Advanced Properties. Host names are used by <a href="Application_layer" title="Application layer">applications</a> such as <a href="Telnet" title="Telnet">telnet</a>, <a href="Ftp" class="mw-redirect" title="Ftp">ftp</a>, <a href="Web_browser" title="Web browser">web browsers</a>, etc. To connect to a computer running the TCP/IP protocol using its name, the host name must be resolved into an <a href="IP_address" title="IP address">IP address</a>, typically by a DNS server. (It is also possible to operate many TCP/IP-based applications, including the three listed above, using only IP addresses, but this is not the norm.)

</p>

<div class="mw-heading mw-heading2"><h2 id="Node_types">Node types</h2></div>

<p>Under Windows, the <b>node type</b> of a networked <a href="Computer" title="Computer">computer</a> relates to the way it resolves NetBIOS names to <a href="IP_address" title="IP address">IP addresses</a>. This assumes that there are any IP addresses for the NetBIOS nodes, which is assured only when NetBIOS operates over NBT; thus, node types are not a property of NetBIOS per se but of interaction between NetBIOS and TCP/IP in the Windows OS environment. There are four node types.

</p>

<ul><li>B-node: 0x01 Broadcast</li>

<li>M-node: 0x04 Mixed (broadcast, then WINS)</li>

<li>H-node: 0x08 Hybrid (WINS, then broadcast)</li></ul>

<p>The node type in use is displayed by opening a <a href="Command_line" class="mw-redirect" title="Command line">command line</a> and typing <i>ipconfig /all</i>.

A <a href="Microsoft_Windows" title="Microsoft Windows">Windows</a> computer registry may also be configured in such a way as to display "unknown" for the node type.

</p>

<div class="mw-heading mw-heading2"><h2 id="NetBIOS_Suffixes">NetBIOS Suffixes</h2></div>

<p>The NetBIOS Suffix, alternately called the NetBIOS End Character (endchar), is the 16th character of a NetBIOS name and indicates service type for the registered name. The number of record types is limited to 255; some commonly used values are:

</p><p>For unique names:

</p>

<ul><li>00: Workstation Service (workstation name)</li>

<li>03: <a href="Windows_Messenger_service" title="Windows Messenger service">Windows Messenger service</a></li>

<li>06: <a href="Remote_Access_Service" class="mw-redirect" title="Remote Access Service">Remote Access Service</a></li>

<li>20: <a href="File_server" title="File server">File Service</a> (also called Host Record)</li>

<li>21: <a href="Remote_Access_Service" class="mw-redirect" title="Remote Access Service">Remote Access Service</a> client</li>

<li>1B: <a href="Windows_Server_domain" class="mw-redirect" title="Windows Server domain">Domain</a> Master <a href="Browser_service" title="Browser service">Browser</a> – Primary Domain Controller for a domain</li>

<li>1D: Master Browser</li></ul>

<p>For group names:

</p>

<ul><li>00: Workstation Service (workgroup/domain name)</li>

<li>1C: <a href="Domain_controller" title="Domain controller">Domain Controllers</a> for a domain (group record with up to 25 IP addresses)</li>

<li>1E: Browser Service Elections</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Protocol_stack">Protocol stack</h2></div>

<p>The following table shows a brief history of NetBIOS and its related protocols. <a href="Server_Message_Block" title="Server Message Block">SMB</a> was the main protocol that used NetBIOS. SMB enables Windows File and Printer Sharing.

</p>

</caption>

<td>7

</td>

<td><a href="Application_layer" title="Application layer">Application layer</a>

</td>

</td>

<td><a href="Windows_Chat" title="Windows Chat">Windows Chat</a>, <a href="ClipBook_Viewer" title="ClipBook Viewer">ClipBook Viewer</a>, <a href="Microsoft_Hearts" title="Microsoft Hearts">Microsoft Hearts</a>

</td>

<td rowspan="2">SMB

</td>

<td rowspan="2">SMB

</td>

<td rowspan="2">SMB

</td>

<td rowspan="3">SMB

</td>

<td rowspan="3">SMB

</td></tr>

<tr>

<td>6

</td>

<td><a href="Presentation_layer" title="Presentation layer">Presentation layer</a>

</td>

<td><a href="NetDDE" class="mw-redirect" title="NetDDE">NetDDE</a>

</td></tr>

<tr>

<td>5

</td>

<td><a href="Session_layer" title="Session layer">Session layer</a>

</td>

<td rowspan="4">NetBIOS (The original "Network Basic Input/Output System")

</td>

<td colspan="2" rowspan="3">NetBIOS (<a href="NetBIOS_Frames" title="NetBIOS Frames">NetBIOS Frames</a>, incorrectly labeled as "NetBEUI" in Windows)

</td>

<td>NetBIOS (NetBIOS over IPX/SPX)

</td>

<td>NetBIOS (<a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NetBIOS over TCP/IP</a>)

</td></tr>

<tr>

<td>4

</td>

<td><a href="Transport_layer" title="Transport layer">Transport layer</a>

</td>

</td>

</td>

</td>

<td><a href="QUIC" title="QUIC">QUIC</a> (over <a href="User_Datagram_Protocol" title="User Datagram Protocol">UDP</a>)

</td></tr>

<tr>

<td>3

</td>

<td><a href="Network_layer" title="Network layer">Network layer</a>

</td>

</td>

</td>

</td>

</td></tr>

<tr>

<td>2

</td>

<td><a href="Data_link_layer" title="Data link layer">Data link layer</a>

</td>

<td colspan="2"><a href="IEEE_802.2" title="IEEE 802.2">IEEE 802.2</a> on <a href="Ethernet" title="Ethernet">Ethernet</a>, <a href="Token_Ring" title="Token Ring">Token Ring</a>

</td>

<td>Any link that carries IPX

</td>

<td>Any link that carries IP

</td>

<td>Any link that carries IP

</td>

<td>Any link that carries IP

</td></tr>

<tr>

<td>1

</td>

<td><a href="Physical_layer" title="Physical layer">Physical layer</a>

</td>

<td><a href="IBM_PC_Network" title="IBM PC Network">IBM PC Network</a>

</td>

<td colspan="2"><a href="Ethernet" title="Ethernet">Ethernet</a>, <a href="Token_Ring" title="Token Ring">Token Ring</a>

</td>

<td>

</td>

<td>

</td>

<td>

</td>

<td>

</td></tr>

<tr>

<td colspan="2">First supported

</td>

<td>

</td>

<td colspan="2">Windows for Workgroups 3.1

</td>

<td>Windows for Workgroups 3.1

</td>

<td>Windows NT 3.5

</td>

<td>Windows 2000

</td>

<td>Windows 11 (Server side requires Windows Server 2022 Datacenter: Azure Edition)

</td></tr>

<tr>

<td colspan="2">Last supported

</td>

<td>

</td>

<td colspan="2">Windows XP (requires manual install)

</td>

<td>Windows XP

</td>

<td>

</td>

<td>

</td>

<td>

</td></tr></tbody></table>

<ul><li><a href="NetBIOS_over_TCP/IP" title="NetBIOS over TCP/IP">NetBIOS over TCP/IP</a> (NBT)</li>

<li><a href="NetBIOS_Frames" title="NetBIOS Frames">NetBIOS Frames</a> (NBF)</li>

<li><a href="Server_Message_Block" title="Server Message Block">Server Message Block</a> (SMB)</li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFSosinsky2009" class="citation book cs1">Sosinsky, Barrie (2009). <span class="id-lock-limited" title="Free access subject to limited trial, subscription normally required"><a rel="nofollow" class="external text" href="https://archive.org/details/networkingbible0000sosi"><i>Networking Bible</i></a></span>. <a href="John_Wiley_%26_Sons" class="mw-redirect" title="John Wiley & Sons">John Wiley & Sons</a>. pp. <a rel="nofollow" class="external text" href="https://archive.org/details/networkingbible0000sosi/page/528/mode/2up">528</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780470543429</bdi>.</cite></span>

</li>

<li id="cite_note-inside_netbios-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-inside_netbios_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-inside_netbios_2-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-inside_netbios_2-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-inside_netbios_2-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-inside_netbios_2-4"><sup><i><b>e</b></i></sup></a> <a href="#cite_ref-inside_netbios_2-5"><sup><i><b>f</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFHaugdahl1990" class="citation book cs1">Haugdahl, J. Scott (June 1990). <a rel="nofollow" class="external text" href="https://bitsavers.org/pdf/ibm/pc/pc_network/Haugdahl_InsideNETBIOS_3ed_1990.pdf"><i>Inside NETBIOS</i></a> <span class="cs1-format">(PDF)</span> (3rd ed.). Architecture Technology Corporation. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-939405-00-8</bdi>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.oreilly.com/library/view/network-security-assessment/9780596510305/ch10.html">"10. Assessing Windows Networking Services - Network Security Assessment, 2nd Edition [Book]"</a>. <i>www.oreilly.com</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230420121049/https://www.oreilly.com/library/view/network-security-assessment/9780596510305/ch10.html">Archived</a> from the original on 20 April 2023<span class="reference-accessdate">. Retrieved <span class="nowrap">20 April</span> 2023</span>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.networking-hardware.com/juniper/service-gateway">"Getaway hardware for protocols"</a>. <i>www.networking-hardware.com</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230326062716/https://www.networking-hardware.com/juniper/service-gateway">Archived</a> from the original on 26 March 2023<span class="reference-accessdate">. Retrieved <span class="nowrap">20 April</span> 2023</span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.os2museum.com/wp/early-microsoft-networks/">"Early Microsoft Networks | OS/2 Museum"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">4 September</span> 2024</span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-wpo/26b6d27b-7470-4a0d-bcfc-88670c6c50d4">"[MS-WPO]: WINS Management Protocol"</a>. <i>learn.microsoft.com</i>. 14 February 2019. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230617123311/https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-wpo/26b6d27b-7470-4a0d-bcfc-88670c6c50d4">Archived</a> from the original on 17 June 2023<span class="reference-accessdate">. Retrieved <span class="nowrap">17 June</span> 2023</span>. <q>Because the NetBIOS protocol, defined in [RFC1002], does not support the mapping between NetBIOS names and IPv6 addresses, the Remote Administrative Interface: WINS protocol applies only to IPv4 addresses. It does not apply to IPv6 addresses.</q></cite></span>

</li>

<li id="cite_note-MS-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-MS_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-MS_7-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and">"Naming conventions in Active Directory for computers, domains, sites, and OUs"</a>. <a href="Microsoft" title="Microsoft">Microsoft</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171222054350/https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and">Archived</a> from the original on 22 December 2017<span class="reference-accessdate">. Retrieved <span class="nowrap">19 December</span> 2017</span>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li>Haugdahl, J. Scott (1990). <i>Inside NetBIOS</i>. Architecture Technology Corp. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>99914-57-34-8</bdi></li>

<li>Silberschatz, Abraham; Galvin, Peter Baer; Gagne, Greg (2004). <i>Operating System Concepts</i>. (7th Ed.). John Wiley & Sons. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-471-69466-5</bdi></li>

<li>Meyers, Michael (2004). "Managing and Troubleshooting Networks". McGraw-Hill. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-07-225665-9</bdi></li>

<li>Tamara Dean. <i>Network+ Guide to Networks</i>, pg. 206 (NetBEUI)</li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://publib.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BK8P7001/CCONTENTS">LAN Technical Reference: 802.2 and NetBIOS APIs</a></li>

<li><a rel="nofollow" class="external text" href="http://ubiqx.org/cifs">Implementing CIFS</a> (from the <a href="Samba_software" class="mw-redirect" title="Samba software">Samba</a> team, published under the <a href="Open_Publication_License" title="Open Publication License">Open Publication License</a>)</li>

<li><a rel="nofollow" class="external text" href="http://timothydevans.me.uk/n2c.html">NetBIOS, NetBEUI, NBF, SMB, CIFS Networking</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20090503083915/http://ourworld.compuserve.com/homepages/timothydevans/osi.htm">Open Systems Interconnection (OSI) Reference Model for NBF, NBT, and NBX</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20081207101027/http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_qxqq.mspx?mfr=true">LMHOSTS File</a></li>

<li><a rel="nofollow" class="external text" href="https://www.betaarchive.com/wiki/index.php/Microsoft_KB_Archive/163409">NETBIOS End Characters / Suffixes</a> – Microsoft Knowledge Base article describing list of NetBIOS Suffixes.</li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20141025202805/http://www.coderbliss.com/2014/10/24/windows-7-netbios-library-in-visual-basic/">Windows 7 NetBIOS Library in Visual Basic - Coder Bliss – Jon Reedholm</a>.</li>

<li><cite id="CITEREFRichard_Sharpe2002" class="citation web cs1">Richard Sharpe (8 October 2002). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20091202045224/http://samba.anu.edu.au/cifs/docs/what-is-smb.html">"Just what is SMB?"</a>. Archived from <a rel="nofollow" class="external text" href="http://samba.anu.edu.au/cifs/docs/what-is-smb.html">the original</a> on 2 December 2009<span class="reference-accessdate">. Retrieved <span class="nowrap">1 January</span> 2012</span>.</cite></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1038841319">

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-label="Navbox599" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Authority control databases: National </th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><span class="rt-commentedText tooltip tooltip-dotted" title="NetBIOS (rozhraní)"><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph508942&CON_LNG=ENG">Czech Republic</a></span></span></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-29" href="https://en.wikipedia.org/wiki/?title=NetBIOS&oldid=1303182851">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>